Repository navigation
Sync shadcn components with the current registry - #72
Merged
Merged
Conversation
Test Results21 tests 21 ✅ 3s ⏱️ Results for commit 91775fa. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sync the installed shadcn components with the current official new-york registry while preserving the starter configuration.
All 56 installed components were compared with CLI-generated upstream source; 52 now use the official cn 0.4.0 package and four were already current. Existing project formatting and lint compatibility comments are preserved, and Recharts stays at the newer validated 3.10.1 release.
Validation passed: 21 tests, TypeScript, production build, formatting, frozen offline install, and browser checks for dialog, select, combobox, calendar, chart rendering, and keyboard resizing. Lint reports zero errors and two existing warnings. The temporary browser verification page was removed. No Cargo build, check, or test was run.